Smart card nfc secure money transfer

ABSTRACT

A secure method of real time money transferring between account holders utilizes Near Field Communication (NFC) technologies, dynamic transaction cards, and a mobile application to facilitate a seamless mobile transfer of funds. The dynamic transaction card of the customer requesting to make the transfer of funds may be placed in contact with the second recipient dynamic transaction card of the customer receiving the funds transfer to establish an NFC connection. The dynamic transaction card requesting the transfer may receive, via the NFC antenna on the card, the recipient customer account information stored on a passive NFC tag. The dynamic transaction card requesting the transfer may transmit the recipient account information to a mobile application, which may transmit the recipient account information to an account provider system for facilitating the funds transfer.

CROSS REFERENCE TO RELATED APPLICATION

The subject application claims the benefit of U.S. Provisional PatentApplication No. 62/440,132, filed on Dec. 29, 2016, the contents ofwhich are hereby incorporated by reference in their entireties.

FIELD OF THE DISCLOSURE

The present disclosure relates to a dynamic transaction card, andsystems and methods relating to the dynamic transaction card. A securemethod of transferring money in real time between account holders at afinancial institution utilizes Near Field Communication (NFC)technologies, dynamic transaction cards, and a mobile application tofacilitate a seamless mobile transfer of funds between account holders.

BACKGROUND OF THE DISCLOSURE

Mobile applications that facilitate electronic transfers of funds havelimited capabilities. Transferring funds between accounts requiresaccessing and transmitting substantial sensitive customer informationfrom customers, including information about the receiving account. Usingthese existing systems, customers need to manually provide customerinformation to complete the transfer. Not only is this burdensome andtime-consuming for customers, but it also leads to the possibility of afailed transfer due to the entering of incorrect customer information,which is a likely occurrence when such information is entered manually.Such transfers can also require significant action on the recipient end,such as the registration for the receipt of funds

Additionally, these methods for transferring funds electronically posegreat security concerns when accessing and transmitting sensitiveaccount information, which may compromise the sensitive data. Currentmalware and phishing attacks can acquire this sensitive accountinformation utilized to transfer funds electronically.

These and other drawbacks exist.

SUMMARY OF THE DISCLOSURE

Various embodiments of the present disclosure provide a dynamictransaction card, systems supporting a dynamic transaction card, andmethods for operating a dynamic transaction card. Specifically,utilizing an NFC connection in combination with a mobile application, afirst account holder may place a first dynamic transaction cardassociated with the first account in contact with a second accountholder's second dynamic transaction card associated with a secondaccount to initiate an instant transfer of funds between the first andsecond account.

As referred to herein, a dynamic transaction card may be understood toinclude a transaction card that may include a number of accounts thatmay be activated and/or deactivated by an account holder and/or accountprovider, data storage that may be updated to reflect real-time and/oron-demand account and/or transaction data, and/or display components todisplay the updated account and/or transaction data. A dynamictransaction card may be understood to be activated (e.g., turned on)and/or deactivated (e.g., turned off) based on input received at thedynamic transaction card as described herein.

A dynamic transaction card may include a smart card, which may beutilized to provide an instant secure money transfer between accountholders without utilizing an external service other than an accountprovider associated with the account holders' system. A user does notneed to enter any customer information because by using dynamictransaction cards to facilitate the money transfer, the customerinformation is obtained automatically via NFC. A customer desiring totransfer funds may utilize a mobile application of a customer mobiledevice that is integrated with the customer dynamic transaction card toselect a transfer amount and may enable active NFC communication mode ona customer dynamic transaction card. A first customer dynamictransaction card may include a secure payment chip, which may be aEuroPay-MasterCard-Visa (EMV™) chip having secure memory, amicroprocessor, which may include a payment processing microprocessor, acommunication device which may include an antenna such as an NFCantenna, and an application processor which may store an application,which when executed may facilitate the processing of the dynamictransaction card. A second dynamic transaction card may include a securepayment chip, which may be an EMV™ chip having a secure memory, amicroprocessor, which may include a payment processing microprocessor, acommunication device which may include an antenna such as an NFC antennaand an application processor. The respective application processor maybe utilized to enable an active communication mode, which may include anactive NFC communication mode, on the dynamic transaction cards.

The first customer dynamic transaction card may receive a request, via ashort range wireless communication network, which may be a Bluetooth™ orBluetooth™ Low Energy (BLE) network from the mobile application executedon the first customer mobile device to transfer funds from this firstcustomer account to a second recipient customer account which isassociated with a second dynamic transaction card. The applicationprocessor on the second dynamic transaction card may be utilized togenerate a passive tag, which may include a passive NFC tag, which maybe utilized to securely store account information in the passive tag. Assuch, the first dynamic transaction card of the customer requesting tomake the transfer of funds may be placed in contact with the secondrecipient dynamic transaction card of the customer receiving the fundstransfer to establish a connection, which may include an NFC connection.For example, utilizing an NFC connection, the first dynamic transactioncard requesting the transfer of funds may receive, via the NFC antennaon the card, the recipient customer account information stored on thepassive NFC tag.

To facilitate the mobile transfer of funds, the first dynamictransaction card requesting the transfer of funds may transmit, via ashort range wireless communication network, which may be a Bluetooth™ orBLE network, the recipient account information to a mobile applicationwhich may be located on a mobile device of the customer requesting thefunds transfer. The mobile application may transmit the recipientaccount information to an account provider system via a wirelessnetwork, which may be a mobile network or WiFi. The account providersystem may be utilized to transfer the requested funds from the firstrequesting account to the second recipient account.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present disclosure, together with furtherobjects and advantages, may best be understood by reference to thefollowing description taken in conjunction with the accompanyingdrawings, in the several Figures of which like reference numeralsidentify like elements, and in which:

FIG. 1 depicts an example embodiment of a system including dynamictransaction cards according to embodiments of the disclosure;

FIG. 2 depicts an example embodiment of a system including dynamictransaction cards according to embodiments of the disclosure;

FIG. 3 depicts an example embodiment of a system including a dynamictransaction card according to embodiments of the disclosure;

FIG. 4 depicts an example card-device linking system according toembodiments of the disclosure; and

FIG. 5 depicts an example method for using dynamic transaction cardsaccording to embodiments of the disclosure.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The entire contents of the following applications are incorporatedherein by reference: U.S. patent application Ser. No. 15/098,585entitled “System, Method and Apparatus for a Dynamic Transaction Card”filed Apr. 14, 2016, which claims the benefit of U.S. ProvisionalApplication No. 62/147,568 filed Apr. 14, 2015 and U.S. ProvisionalApplication No. 62/720,669 filed Dec. 22, 2015; U.S. patent applicationSer. No. 15/098,770 entitled “System, Method, and Apparatus for aDynamic Transaction Card” filed Apr. 14, 2016, which claims the benefitof U.S. Provisional Application No. 62/270,669 filed Dec. 22, 2015 andU.S. Provisional Application No. 62/147,568 filed Apr. 14, 2015; U.S.patent application Ser. No. 15/098,935 entitled “Dynamic TransactionCard Power Management” filed Apr. 14, 2016, which claims the benefit ofU.S. Provisional Application No. 62/147,568 filed Apr. 14, 2015, U.S.Provisional Application No. 62/266,324 filed Dec. 11, 2015, U.S.Provisional Application No. 62/270,307 filed Dec. 21, 2015, and U.S.Provisional Application No. 62/305,599 filed Mar. 9, 2016; U.S. patentapplication Ser. No. 14/977,730 entitled “A System, Method, andApparatus for Locating a Bluetooth Enabled Transaction Card, filed Dec.22, 2015, which claims the benefit of U.S. Provisional Application No.62/095,190, filed on Dec. 22, 2014; U.S. Pat. No. 9,105,025, entitled,Enhanced Near Field Communications Attachment filed on May 29, 2014,which claims the benefit of U.S. Provisional Application No. 61/570,275filed on Dec. 13, 2011 and U.S. Provisional Application No. 61/547,910filed on Oct. 17, 2011; U.S. patent application Ser. No. 14/338,423,entitled “System and Method for Exchanging Data with Smart Cards” filedJul. 23, 2014, which claims the benefit of U.S. Provisional ApplicationNo. 61/857,443 filed on Jul. 23, 2013; U.S. patent application Ser. No.15/098,830 entitled “Dynamic Transaction Card with EMV Interface andMethod of Manufacturing” filed Apr. 14, 2016, which claims the benefitof U.S. Provisional Application No. 62/270,648 filed Dec. 22, 2015 andU.S. Provisional Application No. 62/147,568 filed Apr. 14, 2015; U.S.patent application Ser. No. 14/206,305 entitled “System and Method forProviding Third Party Payments with Non-Integrated Merchants” filed Mar.12, 2014, which claims the benefit of U.S. Provisional Application No.61/778,776 filed Mar. 13, 2015; U.S. patent application Ser. No.14/480,842 entitled “System and Method for Automatically Authenticatinga Caller” filed Sep. 9, 2014, which claims the benefit of U.S.Provisional Application No. 61/875,251 filed Sep. 9, 2013; U.S. patentapplication Ser. No. 15/297,453 entitled “System and Method forAutomatically Authenticating a Caller” filed Oct. 19, 2016, which is acontinuation and claims the benefit of U.S. patent application Ser. No.14/480,842, which claims the benefit of U.S. Provisional Application No.61/875,251; and U.S. patent application Ser. No. 14/827,671 entitled“System and Method for Digital Authentication” filed Aug. 17, 2015,which claims the benefit of U.S. Provisional Application No. 62/037,710filed Aug. 15, 2014.

The following description is intended to convey a thorough understandingof the embodiments described by providing a number of specific exampleembodiments and details involving a dynamic transaction card and systemsand methods for using a dynamic transaction card to utilize an NFCconnection in combination with a mobile application to facilitate asecure instant transfer of funds.

It should be appreciated, however, that the present disclosure is notlimited to these specific embodiments and details, which are examplesonly. It is further understood that one possessing ordinary skill in theart, in light of known systems and methods, would appreciate the use ofthe invention for its intended purposes and benefits in any number ofalternative embodiments, depending on specific design and other needs.An EMV™ enabled card is used as an example of a dynamic transactioncard. A dynamic transaction card may include any type of transactioncard that includes a microcontroller-enabled card used in any type oftransaction, including, for example, debit cards, credit cards, pre-paidcards, cards used in transportation systems, membership programs,loyalty programs, hotel systems, and the like. A dynamic transactioncard may include enhanced features, including hardware, software, andfirmware, beyond the traditional features of a magnetic stripe or EMV™card. The use of “mobile device” in the examples throughout thisapplication is only by way of example. Any type of device capable ofcommunicating with a dynamic transaction card may also be used,including, for example, personal computers, tablets, gaming systems,televisions, or any other device capable of communicating with a dynamictransaction card.

According to the various embodiments of the present disclosure, adynamic transaction card and systems and methods for using a dynamictransaction card are provided. Such embodiments may include, forexample, a transaction card including various components to facilitatethe notifications, alerts, and/or other output on a dynamic transactioncard to an account holder associated with the dynamic transaction card.Notifications, alerts, and output may be provided in the form of LEDlights and/or colors, LED lighting patterns, dot matrix displays, and/orthe like, which as situated on and/or within a dynamic transaction card.Interactive elements of a dynamic transaction card may be activated,triggered, and/or made available via an input component on the dynamictransaction card. For example, a dynamic transaction card may include acapacitive touch sensor, a piezoelectric sensor, via load cells, and/orthe like. These types of sensors may activate, trigger, and/or makeavailable display and/or LED lighting information to alert and/or notifya dynamic transaction card holder.

In various embodiments, providing the alerts, notifications, and/orother output on a dynamic transaction card could be provided with theassistance of a network environment, such as a cellular or Internetnetwork. For example, a mobile device may request and/or receive dataindicative of notifications, alerts, and/or output to be displayed on adynamic transaction card from a financial institution system via anetwork. A mobile device may then relay the data via a network (e.g.,NFC, Bluetooth™, and/or the like) to the dynamic transaction card forstorage and/or to activate, trigger, and/or output notifications and/oralerts.

FIG. 1 depicts an example system 100 including a dynamic transactioncard, which may utilize an NFC connection in combination with a mobileapplication to facilitate a secure instant transfer of funds. As shownin FIG. 1, an example system 100 may include one or more dynamictransaction cards 120, 150, one or more account provider systems 130,and one or more user devices 140.

For example, network 110 may be one or more of a wireless network, awired network or any combination of wireless network and wired network.For example, network 110 may include one or more of a fiber opticsnetwork, a passive optical network, a cable network, an Internetnetwork, a satellite network, a wireless LAN, a Global System for MobileCommunication (“GSM”), a Personal Communication Service (“PCS”), aPersonal Area Network (“PAN”), Wireless Application Protocol (WAP),Multimedia Messaging Service (MMS), Enhanced Messaging Service (EMS),Short Message Service (SMS), Time Division Multiplexing (TDM) basedsystems, Code Division Multiple Access (CDMA) based systems, D-AMPS,Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1, 802.11n and 802.11g,a Bluetooth™ network, or any other wired or wireless network fortransmitting and receiving a data signal.

In addition, network 110 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 902.3, a wide area network (“WAN”), alocal area network (“LAN”), a wireless personal area network (“WPAN”),or a global network such as the Internet. Also network 110 may supportan Internet network, a wireless communication network, a cellularnetwork, or the like, or any combination thereof. Network 110 mayfurther include one network, or any number of the example types ofnetworks mentioned above, operating as a stand-alone network or incooperation with each other. Network 110 may utilize one or moreprotocols of one or more network elements to which they arecommunicatively coupled. Network 110 may translate to or from otherprotocols to one or more protocols of network devices. Although network110 is depicted as a single network, it should be appreciated thataccording to one or more embodiments, network 110 may comprise aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, and home networks.

User device 140 may include, for example, one or more mobile devices,such as, for example, personal digital assistants (PDA), tabletcomputers and/or electronic readers (e.g., iPad™, Kindle Fire™,Playbook™, Touchpad™, etc.), wearable devices (e.g., Google Glass™),telephony devices, smartphones, cameras, music playing devices (e.g.,iPod, etc.), televisions, set-top-box devices, and the like.

Account provider system 130 and user device 140 also may include anetwork-enabled computer system and/or device. As referred to herein, anetwork-enabled computer system and/or device may include, but is notlimited to: e.g., any computer device, or communications deviceincluding, e.g., a server, a network appliance, a personal computer(PC), a workstation, a mobile device, a phone, a handheld PC, a personaldigital assistant (PDA), a thin client, a fat client, an Internetbrowser, or other device. The network-enabled computer systems mayexecute one or more software applications to, for example, receive dataas input from an entity accessing the network-enabled computer system,process received data, transmit data over a network, and receive dataover a network. For example, account provider system may includecomponents such as those illustrated in FIG. 2 and/or FIG. 4.

Account provider system 130 and user device 140 may include at least onecentral processing unit (CPU), which may be configured to executecomputer program instructions to perform various processes and methods.Account provider system 130 and user device 140, may include datastorage, including for example, random access memory (RAM) and read onlymemory (ROM), which may be configured to access and store data andinformation and computer program instructions. Data storage may alsoinclude storage media or other suitable type of memory (e.g., such as,for example, RAM, ROM, programmable read-only memory (PROM), erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), magnetic disks, optical disks,floppy disks, hard disks, removable cartridges, flash drives, any typeof tangible and non-transitory storage medium), where the files thatcomprise an operating system, application programs including, forexample, web browser application, email application and/or otherapplications, and data files may be stored. The data storage of thenetwork-enabled computer systems may include electronic information,files, and documents stored in various ways, including, for example, aflat file, indexed file, hierarchical database, relational database,such as a database created and maintained with software from, forexample, Oracle® Corporation, Microsoft® Excel™ file, Microsoft® Access™file, a solid state storage device, which may include an all flasharray, a hybrid array, or a server-side product, enterprise storage,which may include online or cloud storage, or any other storagemechanism.

Account provider system 130 and user device 140 may further include, forexample, a processor, which may be several processors, a singleprocessor, or a single device having multiple processors. Althoughdepicted as single elements, it should be appreciated that according toone or more embodiments, account provider system 130 and/or user device140, may comprise a plurality of account provider systems 130 and/oruser devices.

Account provider system 130 and user device 140 may further include datastorage, such as data storage 138. The data storage may includeelectronic information, files, and documents stored in various ways,including, for example, a flat file, indexed file, hierarchicaldatabase, relational database, such as a database created and maintainedwith software from, for example, Oracle® Corporation, Microsoft® Excel™file, Microsoft® Access™ file, a solid state storage device, which mayinclude an all flash array, a hybrid array, or a server-side product,enterprise storage, which may include online or cloud storage or anyother storage mechanism.

As shown in FIG. 1, each account provider system 130 and/or user device140 may include various components. As used herein, the term “component”may be understood to refer to computer executable software, firmware,hardware, and/or various combinations thereof. It is noted there where acomponent is a software and/or firmware component, the component isconfigured to affect the hardware elements of an associated system. Itis further noted that the components shown and described herein areintended as examples. The components may be combined, integrated,separated, or duplicated to support various applications. Also, afunction described herein as being performed at a particular componentmay be performed at one or more other components and by one or moreother devices instead of or in addition to the function performed at theparticular component. Further, the components may be implemented acrossmultiple devices or other components local or remote to one another.Additionally, the components may be moved from one device and added toanother device, or may be included in both devices.

As depicted in FIG. 1, system 100 may include dynamic transaction cards120, 150. A dynamic transaction card may include any transaction cardthat is able to display alerts, notifications, and/or other output to acard holder via a display and/or LED lighting 126, 156 and/or receiveinput to interact with the dynamic transaction card via, for example, asensor 124, 154. Although FIG. 1 depicts a single sensor, 124, 154,multiple sensors may be included in dynamic transaction card 120, 150.Dynamic transaction card 12, 150 also may be composed of variousmaterials that enable the entire exterior surface of card 120, 150 toact as a sensor. A dynamic transaction card may be able to communicatewith, for example, a mobile device using RFID, Bluetooth™, NFC, WiFiDirect and/or other related technologies. For example, communicationsbetween a dynamic transaction card and a mobile device may includemethods, systems, and devices described in U.S. Patent Publication No2015-0032635 filed on Jul. 23, 2014, the entire contents of which areincorporated herein by reference.

A dynamic transaction card may be able to communicate with EMV™terminals via contact point positions on the exterior of card 120, 150,such as those positions on an EMV™ standard chip card 122, 152 locatedon the dynamic transaction card 120, 150 or an EMV plate positions onthe exterior of card 120, 150 connected to an EMV™ processor within card120, 150. For example, contact point positions on the exterior of card120, 150 may be directly connected and adjacent to an EMV™ processor(e.g., EMV™ chip 122, 152). In another example, the contact pointpositions on the exterior of card 120, 150 may be connected to an EMV™processor using a form of wired connection (e.g., electrical wiring,plastic jumpers, and/or the like) such that the EMV™ processor may bepositioned at any location in the interior of card 120, 150 as describedin U.S. Provisional Application 62/270,648, the entire contents of whichare incorporated herein by reference.

A dynamic transaction card 120, 150 may also include hardware componentsto provide contactless payments and/or communications. For example,dynamic transaction card 120, 150 may include an output layer, an outerprotective layer, potting, application (e.g., a Java™ Applet),application integration (e.g., Java Applet integration), an EMV™ chip122, 152, one or more sensors, a display, a display driver, firmware, abootloader, a microcontroller, one or more antenna, an energy storagecomponent, power management, a flexible PCB, a chassis, and/or cardbacking. An EMV™ chip 122, 152 embedded in the dynamic transaction card120, 150 may include a number of contacts that may be connected andactivated using an interface device.

Account provider system 130 may include systems associated with, forexample, a banking service company such as Capital One®, Bank ofAmerica®, Citibank®, Wells Fargo®, Sun Trust™, various community banks,and the like, as well as a number of other financial institutions suchas Visa®, MasterCard®, and American Express® that issue credit and/ordebit cards, for example, as transaction cards. Account provider system130 may include and/or be connected to one or more computer systems andnetworks to process transactions. For example, account provider system130 may process transactions as shown and described in FIG. 5 below.Account provider system 130 may include systems associated withfinancial institutions that issue transaction cards, such as a dynamictransaction card 120, 150, and maintains a contract with cardholders forrepayment. In various embodiments, an account provider system 130 mayissue credit, debit, and/or stored value cards, for example. Accountprovider system 130 may include, by way of example and not limitation,depository institutions (e.g., banks, credit unions, building societies,trust companies, mortgage loan companies, pre-paid gift cards or creditcards, etc.), contractual institutions (e.g., insurance companies,pension funds, mutual funds, etc.), investment institutions (e.g.,investment banks, underwriters, brokerage funds, etc.), and othernon-bank financial institutions (e.g., pawn shops or brokers, cashier'scheck issuers, insurance firms, check-cashing locations, payday lending,currency exchanges, microloan organizations, crowd-funding orcrowd-sourcing entities, third-party payment processors, etc.).

Account provider system 130 may include an input/output device 132, atransaction system 134, a dynamic transaction card system 136, and datastorage 138. Input/output device 132 may include for example, I/Odevices, which may be configured to provide input and/or output toproviding party system 130 (e.g., keyboard, mouse, display, speakers,printers, modems, network cards, etc.). Input/output device 132 also mayinclude antennas, network interfaces that may provide or enable wirelessand/or wire line digital and/or analog interface to one or morenetworks, such as network 110, over one or more network connections, apower source that provides an appropriate alternating current (AC) ordirect current (DC) to power one or more components of account providersystem 130, and a bus that allows communication among the variouscomponents of account provider system 130. Input/output device 132 mayinclude a display, which may include for example output devices, such asa printer, display screen (e.g., monitor, television, and the like),speakers, projector, and the like. Although not shown, each accountprovider system 130 may include one or more encoders and/or decoders,one or more interleavers, one or more circular buffers, one or moremultiplexers and/or de-multiplexers, one or more permuters and/ordepermuters, one or more encryption and/or decryption units, one or moremodulation and/or demodulation units, one or more arithmetic logic unitsand/or their constituent parts, and the like.

Transaction system 134 may include various hardware and softwarecomponents to communicate between a merchant, acquisition system,account provider system, and/or a user device to process a transaction,such as a user purchase. Dynamic transaction card system 136 may includevarious hardware and software components, such as data storage (notshown) to store data associated with a dynamic transaction card (e.g.,card number, account type, account balance, account limits, budget data,recent transactions, pairing data such as time and date of pairing witha mobile device, and the like) and cardholder data (e.g., cardholdername, address, phone number(s), email address, demographic data, and thelike). Data storage 138 may store data associated with an account (e.g.,card number, account type, account balance, account limits, budget data,recent transactions, pairing data such as time, date, and location ofpairing with a mobile device, and the like) and account holder data(e.g., account holder name, address, phone number(s), email address,demographic data, and the like).

A user device 140, may include a mobile device, and may be any devicecapable of communicating with a transaction card 120, 150 via, forexample, Bluetooth™ technology, NFC technology, WiFi Direct technology,and/or the like and execute various functions to transmit and receiveaccount data (e.g., card number, account type, account balance, accountlimits, budget data, recent transactions, and/or the like) associatedwith dynamic transaction card 120, 150. For example, user device 140could be an iPhone™, iPad™, and/or Apple Watch™ from Apple® or any othermobile device running Apple's iOS operating system, any device runningGoogle's Android® operating system, including, for example, smartphonesrunning the Android® operating system and other wearable mobile devices,such as Google Glass™ or Samsung Galaxy Gear Smartwatch™, any devicerunning Microsoft's Windows® Mobile operating system, and/or any othersmartphone or like device.

User device 140 may include for example, an input/output device 142, adynamic card system 144, a transaction system 146, and a mobileapplication 148. Input/output device 142 may include, for example, aBluetooth™ device or chipset with a Bluetooth™ transceiver, a chip, andan antenna. The transceiver may transmit and receive information via theantenna and an interface. The chip may include a microprocessor thatstores and processes information specific to a dynamic transactiondevice and provides device control functionality. Device controlfunctionality may include connection creation, frequency-hoppingsequence selection and timing, power control, security control, polling,packet processing, and the like. The device control functionality andother Bluetooth™-related functionality may be supported using aBluetooth™ API provided by the platform associated with the user device140 (e.g., The Android platform, the iOS platform). Using a Bluetooth™API, an application stored on a mobile device 140 (e.g., a bankingapplication, a financial account application, etc.) or the device may beable to scan for other Bluetooth™ devices (e.g., a dynamic transactioncard 120, 150), query the local Bluetooth™ adapter for paired Bluetooth™devices, establish RFCOMM channels, connect to other devices throughservice discovery, transfer data to and from other devices or atransaction card 120, 150, and manage multiple connections. A Bluetooth™API used in the methods, systems, and devices described herein mayinclude an API for Bluetooth™ Low Energy (BLE) to provide significantlylower power consumption and allow a mobile device 140 to communicatewith BLE devices that have low power requirements, such dynamictransaction card 120, 150.

Input/output device 142 may include for example, I/O devices, which maybe configured to provide input and/or output to mobile device 140 (e.g.,keyboard, mouse, display, speakers, printers, modems, network cards,etc.). Input/output device 142 also may include antennas, networkinterfaces that may provide or enable wireless and/or wire line digitaland/or analog interface to one or more networks, such as network 110,over one or more network connections, a power source that provides anappropriate alternating current (AC) or direct current (DC) to power oneor more components of mobile device 140, and a bus that allowscommunication among the various components of mobile device 140.Input/output device 142 may include a display, which may include forexample output devices, such as a printer, display screen (e.g.,monitor, television, and the like), speakers, projector, and the like.Although not shown, each mobile device 140 may include one or moreencoders and/or decoders, one or more interleavers, one or more circularbuffers, one or more multiplexers and/or de-multiplexers, one or morepermuters and/or depermuters, one or more encryption and/or decryptionunits, one or more modulation and/or demodulation units, one or morearithmetic logic units and/or their constituent parts, and the like.

Input/output device 142 may also include an NFC antenna and secureelement (SE). The SE may be a hardware chip specially designed to betamper proof. In one embodiment, the SE may be used for digitally andphysically secure storage of sensitive data, including transaction carddata, payment data, health records, car key identifiers, etc. The SEmay, for example, store information related to a person, customer,financial institution, or other entity. The SE may store informationrelated to a financial account, such as, for example, transaction carddata (e.g., a credit card number, debit account number, or other accountidentifier, account balance, transaction history, account limits, budgetdata, recent transactions, and/or the like). The SE may include acomputer processor or other computational hardware or software. As oneexample, the secure element may contain the Visa® and MasterCard®applications for PayWave® and PayPass® transactions. A secure elementmay take the form of a universal integrated circuit card (UICC) and/or amicroSD card. A UICC may identify a user to a wireless operator, storecontacts, enable secure connections, and add new applications andservices, such as a transaction system.

Input/output device 142 may enable Industry Standard NFC PaymentTransmission. For example, the input/output device 142 may enable twoloop antennas to form an air-core transformer when placed near oneanother by using magnetic induction. Input/output device 142 may operateat 13.56 MHz or any other acceptable frequency. Also, input/outputdevice 142 may provide for a passive communication mode, where theinitiator device provides a carrier field, permitting answers by thetarget device via modulation of existing fields. Additionally,input/output device 142 also may provide for an active communicationmode by allowing alternate field generation by the initiator and targetdevices.

Input/output device 142 may deactivate the RF field while awaiting data.The attachment may use Miller-type coding with varying modulations,including 100% modulation. The attachment may also use Manchester codingwith varying modulations, including a modulation ratio of 10%.Additionally, the attachment may be capable of receiving andtransmitting data at the same time, as well as checking for potentialcollisions when the transmitted signal and received signal frequenciesdiffer.

Input/output device 142 may be capable of utilizing standardizedtransmission protocols, for example but not by way of limitation,ISO/IEC 14443 A/B, ISO/IEC 18092, MiFare™, FeliCa™, tag/smartcardemulation, and the like. Also, input/output device 142 may be able toutilize transmission protocols and methods that are developed in thefuture using other frequencies or modes of transmission. Input/outputdevice 142 may also be backwards-compatible with existing techniques,for example RFID. Also, the system may support transmission requirementsto meet new and evolving standards including internet based transmissiontriggered by NFC.

Dynamic transaction card system 144 may work with input/output device142 to generate and receive account data associated with a dynamictransaction card 120, 150. For example, dynamic transaction card systemmay include various hardware and software components such as a processorand data storage to store dynamic transaction card data (e.g.,cardholder name, address, phone number(s), email address, demographicdata, card number, account type, account balance, account limits, budgetdata, recent transactions and the like).

Transaction system 146 may include various hardware and softwarecomponents, such as data storage and a processor that may work withinput/output device 142 to communicate between a merchant, acquisitionsystem, account provider system, and/or a mobile device to process atransaction, such as a user purchase.

Mobile device 140 may also include various software components tofacilitate the operation of a dynamic transaction card 120, 150. Forexample, mobile device 140 may include an operating system such as, forexample, the iOS operating system from Apple, the Google Android™operating system, and the Windows Mobile™ operating system fromMicrosoft. Mobile device 140 may also include, without limitation,software applications such as mobile banking applications and financialinstitution application to facilitate use of a dynamic transaction card120, 150, an NFC application programming interface, and software toenable touch sensitive displays. Mobile banking applications and/orfinancial institution applications may be combined and/or separate froma dynamic transaction card system 144. Mobile device manufacturers mayprovide software stacks or Application Programming Interfaces (APIs)which allow software applications to be written on top of the softwarestacks. For example, mobile device manufacturers may provide, withoutlimitation, a card emulation API to enable NFC card emulation mode, alogic link control protocol (LLCP) API for peer-to-peer communicationbetween mobile devices, a Bluetooth™ API supporting BLE, and a real-timedata (RTD) API and a NFC Data Exchange Format (NDEF) API forreading/writing.

Software applications on user device 140 may include, for example,mobile application 148, which may be integrated with or separate from amobile wallet application, which may be utilized to by a customerrequesting a transfer of funds to select a transfer amount and to enablean active NFC communication mode on the associated dynamic transactioncard. A customer client device 120 may communicate with account providersystem 130 via mobile application 148.

Software applications on mobile device 140, such as mobile bankingapplications and applications associated with a dynamic transaction card120, 150, may include card on/off features that allow a cardholderassociated with a mobile device 140 to enable and disable a transactioncard. For example, a card holder may use, for example, a mobile bankingapplication stored on a user device 140 to disable and/or enableaccounts associated with a dynamic transaction card 120, 150. A mobilebanking application may include, for example, an application asdisplayed on mobile device 320 in FIG. 3. In this example, a dynamictransaction card 120, 150 may have account data pre-stored on thedynamic transaction card 120, 150 to associate a number of differentaccounts with the dynamic transaction card (e.g., debit card, creditcard, prepaid card, and/or the like). If a card holder has a creditaccount established and desires to establish a debit card associatedwith the dynamic transaction card 120, 150, the card holder may use amobile device 140 and/or dynamic transaction card 120, 150 to activatethe inactive debit account on the dynamic transaction card 120, 150.

Dynamic transaction card 120, 150 may include firmware and/or abootloader. A bootloader may include code to be executed as a dynamictransaction card 200 is activated and before any operating system,firmware, or other code is executed on the dynamic transaction card 120,150. A bootloader may be activated via a sensor and energy storagecomponent of the dynamic transaction card 120, 150. A bootloader may beactivated and/or load an application and/or program upon detection thatcard 120, 150 has been inserted into a terminal, charger, and/or thelike. A bootloader may be activated using only one technique describedherein, using multiple techniques described herein, and/or using a cardholder or card provider selected technique(s) described herein. Abootloader may only be active during a short interval after the card 200powers up. Dynamic transaction card 120, 150 may also be activated usingprogram code that may be flashed directly to a microprocessor such as amicrocontroller, EMV™ processor, and/or the like. Dynamic transactioncard 120, 150 may not use a bootloader but instead may cycle between asleep state and an active state using program code and/or memory.

A dynamic transaction card 120, 150 may include a microcontroller and anantenna. An antenna may include, for example, a loop antenna, a fractalantenna, and/or the like. An antenna may transmit to and receive signalsfrom a mobile device, such as user device 140, to conduct transactionsand display data as described throughout the specification. Amicrocontroller may communicate with an EMV™ chip, Java™ Applet, Java™Applet integration, sensor(s), power management, antenna, energy storagecomponent, display, display driver, firmware, bootloader, and/or anyother component of dynamic transaction card 120, 150. A microcontrollermay control the card operations to conduct transactions and/or displaydata as described throughout this specification.

FIG. 2 illustrates a system associated with the use of a dynamictransaction card. The example system 200 in FIG. 2 may enable afinancial institution, for example, to provide network services to itscardholders, and may include providing transaction card data, accountdata, and/or any other data to a mobile device that may in turn providethat data to a dynamic transaction card. For example, a financialinstitution may include a front-end controlled domain 206, a back-endcontrolled domain 212, and a backend 218 as part of account providersystem 130, a user device 202 may include user device 140, and a dynamictransaction card may include dynamic transaction card 120, 150.Referring to FIG. 4, for example, a dynamic transaction card may besimilar to a dynamic transaction card of cardholder 402; a financialinstitution may include a front-end controlled domain 406, a back-endcontrolled domain 412, and a backend 418 as part of card issuer system418 and/or association/interchange 416; and a mobile device may besimilar to a mobile device of cardholder 402.

The example system 200 also may enable a merchant, for example, toprovide network services to its customers, and may include providingsales, loyalty account data, and/or any other data to a mobile devicethat may in turn provide that data to a dynamic transaction card. Forexample, a mobile device 202 and/or dynamic transaction card mayinteract with a merchant system, such as merchant system to send and/orreceive data to the merchant system, which may interact with a financialinstitution over a network, where a financial institution may include afront-end controlled domain 206, a back-end controlled domain 212, and abackend 218.

System 200 may include a user device 202, a network 204, a front-endcontrolled domain 206, a back-end controlled domain 212, and a backend218. Front-end controlled domain 206 may include one or more loadbalancers 208 and one or more web servers 210. Back-end controlleddomain 212 may include one or more load balancers 214 and one or moreapplication servers 216.

User device 202 may be a network-enabled computer. As referred toherein, a network-enabled computer may include, but is not limited to:e.g., any computer device, or communications device including, e.g., aserver, a network appliance, a personal computer (PC), a workstation, amobile device, a phone, a handheld PC, a personal digital assistant(PDA), a thin client, a fat client, an Internet browser, or otherdevice. The one or more network-enabled computers of the example system200 may execute one or more software applications to enable, forexample, network communications.

User device 202 may include a mobile device, and may include an iPhone™,iPod™, iPad™ from Apple® or any other mobile device running Apple's iOS™operating system, any device running Google's Android® operating system,including for example, Google's wearable device, Google Glass™, anydevice running Microsoft's Windows® Mobile operating system, and/or anyother smartphone or like wearable mobile device. User device 202 alsomay be similar to user device 140 as shown and described in FIG. 1.

Network 204 may be one or more of a wireless network, a wired network,or any combination of a wireless network and a wired network. Forexample, network 204 may include one or more of a fiber optics network,a passive optical network, a cable network, an Internet network, asatellite network, a wireless LAN, a Global System for MobileCommunication (GSM), a Personal Communication Service (PCS), a PersonalArea Networks, (PAN), D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b,802.15.1, 802.11n, and 802.11g or any other wired or wireless networkfor transmitting and receiving a data signal.

In addition, network 204 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 902.3, a wide area network (WAN), alocal area network (LAN) or a global network such as the Internet. Also,network 204 may support an Internet network, a wireless communicationnetwork, a cellular network, or the like, or any combination thereof.Network 204 may further include one network, or any number of exampletypes of networks mentioned above, operating as a stand-alone network orin cooperation with each other. Network 204 may utilize one or moreprotocols of one or more network elements to which they arecommunicatively couples. Network 204 may translate to or from otherprotocols to one or more protocols of network devices. Although network204 is depicted as a single network, it should be appreciated thataccording to one or more embodiments, network 204 may comprise aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, and home networks.

Front-end controlled domain 206 may be implemented to provide securityfor backend 218. Load balancer(s) 208 may distribute workloads acrossmultiple computing resources, such as, for example computers, a computercluster, network links, central processing units or disk drives. Invarious embodiments, load balancer(s) 210 may distribute workloadsacross, for example, web server(s) 216 and/or backend 218 systems. Loadbalancing aims to optimize resource use, maximize throughput, minimizeresponse time, and avoid overload of any one of the resources. Usingmultiple components with load balancing instead of a single componentmay increase reliability through redundancy. Load balancing is usuallyprovided by dedicated software or hardware, such as a multilayer switchor a Domain Name System (DNS) server process.

Load balancer(s) 208 may include software that monitoring the port whereexternal clients, such as, for example, user device 202, connect toaccess various services of a financial institution, for example. Loadbalancer(s) 208 may forward requests to one of the application servers216 and/or backend 218 servers, which may then reply to load balancer208. This may allow load balancer(s) 208 to reply to mobile device 202without mobile device 202 ever knowing about the internal separation offunctions. It also may prevent mobile devices from contacting backendservers directly, which may have security benefits by hiding thestructure of the internal network and preventing attacks on backend 218or unrelated services running on other ports, for example.

A variety of scheduling algorithms may be used by load balancer(s) 208to determine which backend server to send a request to. Simplealgorithms may include, for example, random choice or round robin. Loadbalancers 208 also may account for additional factors, such as aserver's reported load, recent response times, up/down status(determined by a monitoring poll of some kind), number of activeconnections, geographic location, capabilities, or how much traffic ithas recently been assigned.

Load balancers 208 may be implemented in hardware and/or software. Loadbalancer(s) 208 may implement numerous features, including, withoutlimitation: asymmetric loading; Priority activation: SSL Offload andAcceleration; Distributed Denial of Service (DDoS) attack protection;HTTP/HTTPS compression; TCP offloading; TCP buffering; direct serverreturn; health checking; HTTP/HTTPS caching; content filtering;HTTP/HTTPS security; priority queuing; rate shaping; content-awareswitching; client authentication; programmatic traffic manipulation;firewall; intrusion prevention systems.

Web server(s) 210 may include hardware (e.g., one or more computers)and/or software (e.g., one or more applications) that deliver webcontent that can be accessed by, for example a client device (e.g., userdevice 202) through a network (e.g., network 204), such as the Internet.In various examples, web servers, may deliver web pages, relating to,for example, online banking applications and the like, to clients (e.g.,user device 202). Web server(s) 210 may use, for example, a hypertexttransfer protocol (HTTP/HTTPS or sHTTP) to communicate with mobiledevice 302. The web pages delivered to client device may include, forexample, HTML documents, which may include images, style sheets andscripts in addition to text content.

A user agent, such as, for example, a web browser, web crawler, ornative mobile application, may initiate communication by making arequest for a specific resource using HTTP/HTTPS and web server 210 mayrespond with the content of that resource or an error message if unableto do so. The resource may be, for example a file on stored on backend218. Web server(s) 210 also may enable or facilitate receiving contentfrom mobile device 302 so mobile device 202 may be able to, for example,submit web forms, including uploading of files.

Web server(s) also may support server-side scripting using, for example,Active Server Pages (ASP), PHP, or other scripting languages.Accordingly, the behavior of web server(s) 210 can be scripted inseparate files, while the actual server software remains unchanged.

Load balancers 214 may be similar to load balancers 208 as describedabove.

Application server(s) 216 may include hardware and/or software that isdedicated to the efficient execution of procedures (e.g., programs,routines, scripts) for supporting its applied applications. Applicationserver(s) 216 may comprise one or more application server frameworks,including, for example, Java application servers (e.g., Java platform,Enterprise Edition (Java EE), the .NET framework from Microsoft®, PHPapplication servers, and the like). The various application serverframeworks may contain a comprehensive service layer model. Also,application server(s) 216 may act as a set of components accessible to,for example, a financial institution, or other entity implementingsystem 200, through an API defined by the platform itself. For Webapplications, these components may be performed in, for example, thesame running environment as web server(s) 210, and application servers216 may support the construction of dynamic pages. Application server(s)216 also may implement services, such as, for example, clustering,fail-over, and load-balancing. In various embodiments, where applicationserver(s) 216 are Java application servers, the web server(s) 216 maybehaves like an extended virtual machine for running applications,transparently handling connections to databases associated with backend218 on one side, and, connections to the Web client (e.g., user device202) on the other.

Backend 218 may include hardware and/or software that enables thebackend services of, for example, a financial institution, merchant, orother entity that maintains a distributed system similar to system 200.For example, backend 218 may include, a system of record, online bankingapplications, a rewards platform, a payments platform, a lendingplatform, including the various services associated with, for example,auto and home lending platforms, a statement processing platform, one ormore platforms that provide mobile services, one or more platforms thatprovide online services, a card provisioning platform, a general ledgersystem, and/or a location system, which may include additionalcapabilities, such as transaction card data generation, transactionprocessing, and/or transmission of account and/or transaction data.Backend 218 may be associated with various databases, including accountdatabases that maintain, for example, cardholder information (e.g.,demographic data, credit data, cardholder profile data, and the like),transaction card databases that maintain transaction card data (e.g.,transaction history, account balance, spending limit, budget categories,budget spending, budget limits, and the like), and the like. Backend 218also may be associated with one or more servers that enable the variousservices provided by system 200. Backend 218 may enable a financialinstitution to implement various functions associated with reprogramminga transaction card and/or providing data to a transaction card in orderto provide a dynamic display as shown and described herein.

A dynamic display may be a display that is altered by activating newcard data such as, a new card number, a new security code (e.g., CCVcode), a new expiration date, and/or other card/account data. A dynamicdisplay may be a display that is altered by activating new account data,such as a new account number, a new card number, a new security code, anew expiration date, and/or other card/account data. New account and/ornew card data may be fully pre-loaded, partially pre-loaded, and/orreceived from a wireless connection.

For example, fully pre-loaded data may include a full account number,card number, security code, expiration date, and/or other account datathat is loaded onto a dynamic transaction card (e.g., dynamictransaction card 120, 150) upon personalization at a backend facility.Fully pre-loaded data may also include an associated applet thatinteracts with the account and/or card data to execute transactions,manipulate dynamic displays, and/or perform any of the functionalitydescribed herein. Fully pre-loaded data may be activated upon receivingan activation signal from, for example, an account holder device via awireless connection. A wireless device may receive an activation signalfrom an issuing financial institution via a network connection using,for example, a mobile application and/or mobile-enhanced websiteassociated with the issuing financial institution.

Partially pre-loaded data may include a shell account that includes aplaceholder for each type of data required for a fully-functionalaccount (e.g., account holder data, account number, security code,expiration date, and/or the like). A placeholder may include one or morealphanumeric characters associated with inactive, null, or shellaccounts in a backend system associated with the issuing financialinstitution. Partially pre-loaded data may include an associated appletthat interacts with the account and/or card data to executetransactions, manipulate dynamic displays, and/or perform any of thefunctionality described herein. Partially pre-loaded data may beactivated upon receiving an activation signal and/or new card or newaccount data from, for example, an account holder device via a wirelessconnection or a contact connection (e.g., using a terminal in contactwith an EMV™ processor and/or other microchip). A wireless device mayreceive an activation signal and/or new card or new account data from anissuing financial institution via a network connection using, forexample, a mobile application and/or mobile-enhanced website associatedwith the issuing financial institution.

Data transmitted may be encrypted. Encryption/decryption may occur usinga key that was preloaded onto the dynamic transaction card uponpersonalization at the issuing financial institution and/or a keypreloaded to an EMV™ circuit. Data received may include new accountand/or card data. For example, where partially pre-loaded card and/oraccount data are stored on a dynamic transaction card, new card and/oraccount data may be received from an account holder's mobile device viaa wireless connection (e.g., BLE, NFC, WiFi, and/or the like) or acontact connection (e.g., using a terminal in contact with an EMV™processor and/or other microchip). Data received may include an appletand/or applet data required to execute transactions, manipulate dynamicdisplays, and/or perform any of the functionality described herein.

Also, fully pre-loaded and/or partially pre-loaded data may also includekeys (e.g., public/private key pairs, private key pairs, and/or thelike) that may be used by an EMV™ circuit to execute transactions usingthe EMV™ processor on the card.

FIG. 3 illustrates a system associated with the use of a dynamictransaction card. The example system 300 in FIG. 3 may enable a mobiledevice 320 storing a mobile banking application, for example, to providedata updates to a dynamic transaction card 310 via network 330. Forexample, data received at mobile device 320 may be transmitted todynamic transaction card 310 where it is received via antenna 314. Datamay be received and/or transmitted using, for example a mobile bankingapplication that maintains and/or creates a secure connection with afinancial institution to send and/or receive data related to an accountassociated with the financial institution. For example, a mobile bankingapplication may include send and/or receive data related to a creditaccount, a debit account, a prepaid account, a loyalty account, arewards account, and/or the like. Data may also include track data thatmay be updated upon demand.

A mobile application may be utilized by a customer to select a transferamount when making a request to transfer funds to another accountholder.The mobile application may also be utilized to activate active NFCcommunication mode on a dynamic transaction card. The mobile applicationmay communicate with a dynamic transaction card via Bluetooth™ or BLE,and may communicate with the backend account provider system via mobilenetworks or WiFi.

Upon activation of dynamic transaction card via, for example, a sensor318, a data request may be transmitted to a mobile device 320 forupdated information, where mobile device 320 may request updated datafrom a financial institution (not shown). Data received at dynamictransaction card 310 may be stored on microchip 312 and/or may bedisplayed via display 316.

FIG. 4 illustrates an example system 400 and method for a secure mobilemonetary transfer. As shown and described in FIG. 4, account holders,such as account holders associated with a dynamic transaction cardsimilar to dynamic transaction card 120, 150 and/or a mobile devicesimilar to mobile device 140 and financial institutions similar toaccount provider system 130 may be connected with a card associationnetwork to enable secure transactions, timely payments, and successfulwithdrawals. System 400 may include a cardholder 402, merchant 404,Acquirer 410, Association/Interchange 416, and card issuer 418.

Cardholder 402 may be any account holder, including a credit cardholder, debit card holder, stored value card holder and the like.Cardholder 402 may be similar to the card holder associated with dynamictransaction card 120, 150 and/or mobile device 140. Cardholder 402 maypossess a plastic card or carry a device (e.g., a mobile device) thatsecurely stores card credentials and is capable of transmitting the cardcredentials to, for example, a merchant system (e.g., merchant card 406)and/or an input/output device. Cardholder 402 may interact with amerchant and/or a providing party (e.g., merchant 404) by presenting atransaction card (e.g., dynamic transaction card 120, 150) or cardcredentials to a merchant (e.g., merchant card 406).

Merchant 404 may be any merchant that accepts payment from a cardholder402 in exchange for goods, for example. Merchant 404 may be anyretailer, service provider, business entity, or individual that acceptspayments. Merchant 404 may include software, firmware and hardware foraccepting and/or processing payments. For example, as illustrated inFIG. 4, merchant 404 may include a merchant card 406 and a merchantdevice 408, which may include a payment gateway. Terminal 406 andpayment gateway 408 may comprise the physical or virtual device(s) usedby merchant 404 to communicate information to front-end processor 412 ofacquirer 410. In various embodiments, payment gateway 408 may be ane-commerce application service provider service that authorizes paymentsfor merchants. As such, payment gateway 408 may be a virtual equivalentof a PoS terminal and interface with, for example, a billing system ofmerchant 404 and pass data to front-end processor 412 of acquirer 410.

For example a merchant may utilize a merchant smart card to facilitate apayment from an account holder by use of an account holder dynamictransaction card using the secure money transfer methods describedherein.

Acquirer 410 may be, for example, a financial institution or bank thatholds the contract for providing payment processing services to merchant404. Merchant 404 may have a merchant account that may serve as acontract under which Acquirer 410 may extend a line of credit to amerchant who wishes to accept, for example, credit card transactions. Asshown in FIG. 4, Acquirer 410 may be associated with front-end processor412 and back-end processor 414.

In various examples, front-end processor 412 may be a platform that cardterminal 406 and/or payment gateway 408 communicate with when approvinga transaction. Front-end processor 412 may include hardware, firmware,and software to process transactions. Front-end processor 412 may beresponsible for the authorization and capture portion of credit cardtransaction. Front-end processor 412 also may include additionalfront-end platform interconnections to support, for example, ACH anddebit transactions.

Backend processor 414 may be a platform that takes captured transactionsfrom front-end processor 412 and settles them through an Interchangesystem (e.g., association/interchange 416). Back-end processor 414 maygenerate, for example, daily ACH files for merchant settlement. Back-endprocessor 414 also may handle chargeback handling, retrieval request andmonthly statements.

Association/interchange 416 may be the consumer payment system whosemembers are the financial institutions that issue payment cards and/orsign merchant to accept payment cards. Example associations/interchanges416 may include, Visa®, MasterCard®, and American Express®.Association/interchange 416 may include one or more computer systems andnetworks to process transactions.

Issuer 418 may be a financial institution that issues payment cards andmaintains a contract with cardholders for repayment. In variousembodiments, issuer 418 may issue credit, debit, and/or stored valuecards, for example. Example issuers may include, Capital One®, Bank ofAmerica®, Citibank®, Sun Trust®, and the like.

In various embodiments, processing a payment card transaction mayinvolve two stages: (1) authorization and (2) clearing and settlement.Authorization may refer to an electronic request that is sent throughvarious parties to either approve or decline the transaction. Clearingand Settlement may refer to settlement of the parties' settle accountsto enable the parties to get paid.

During authorization, cardholder 402 may present payment card, such asdynamic transaction card 120, 150, as payment (401A) at merchant 404 PoSterminal 406, for example. Merchant 404 may enter card into a physicalPoS terminal 406 (e.g., an EMV™ terminal) or submit a credit cardtransaction to a payment gateway 408 on behalf of withdrawing party 402via secure connection from a Web site, retail location, or a wirelessdevice.

Payment gateway 408 may receive the secure transaction information(403A) and may pass the secure transaction information (405A) via asecure connection to the merchant acquirer's 410 front-end processor412.

Front-end processor 412 may submit the transaction (407A) toassociation/interchange 416 (e.g., a network of financial entities thatcommunicate to manage the processing, clearing and settlement of creditcard transactions). Association/interchange 416 may route thetransaction (409A) to the customer's Issuer 418. Issuer 418 may approveor decline the transaction and passes the transaction results back(411A) through association/interchange 416. Association/interchange thenmay relay the transaction results (413A) to front-end processor 412.

Front-end processor 412 may relay the transaction results (415A) back tothe payment gateway 408 and/or terminal 406. Payment gateway 408 maystore the transaction results and sends them to merchant 404. Merchant404 may receive the authorization response and complete the transactionaccordingly.

During settlement, merchant 404 may deposit the transaction receipt(421S) with acquirer 410 via, for example, a settlement batch. Capturedauthorizations may be passed (923S) from front-end processor 412 to theback-end processor 414 for settlement. Back-end processor may generateACH files for merchant settlement. Acquirer may submit settlement files(425S, 427S) to Issuer 418 for reimbursement via association/interchange416. Issuer 418 may post the transaction and/or withdrawal and paymerchant 404 (429S, 431S, 433S).

FIG. 5 illustrates an example method of utilizing an NFC connection incombination with a mobile application to facilitate a secure real timetransfer of funds between accounts. The method 500 may start at block502. At block 504, a mobile application on a customer mobile device of acustomer desiring to transfer funds may receive a request to transferfunds from a first customer account (customer 1) to a second customeraccount (customer 2). A customer desiring to transfer funds may utilizea mobile application on a customer mobile device that is integrated withthe customer dynamic transaction card to select a transfer amount andmay enable active NFC communication mode on a customer dynamictransaction card. The recipient of the funds may utilize a mobileapplication on a second customer mobile device, which via a pushnotification, may receive a notification from the mobile application onthe first customer mobile device that a request has been made totransfer funds to the second recipient customer. The mobile applicationmay prompt the second recipient customer to select an account to whichthe money may be transferred. Additionally, the second recipientcustomer may utilize the mobile application to set a default account formoney transfers that may be stored in a user profile generated for thesecond recipient customer and may be stored on the account providersystem data storage.

The customer dynamic transaction cards may include a front-end NFCchipset and a loop antenna, which may include a 13.56 MHz loop antenna.The customer dynamic transaction cards may receive a request, via aBluetooth™ or Bluetooth™ Low Energy (BLE) network from the mobileapplication executed on the customer mobile device to transfer fundsfrom this first customer account to a second recipient customer accountwhich is associated with a second dynamic transaction card. The customermobile device may receive a response from the customer dynamictransaction card confirming a wireless connection between the twodevices. The wireless connection may be using NFC technologies,Bluetooth™ technologies, and/or BLE technologies as described herein.

In an exemplary embodiment, the system may enable Industry Standard NFCTransmission. For example, an NFC attachment, included on the dynamictransaction cards, may enable two loop antennas to form an air-coretransformer when placed near one another by using magnetic induction.The system may operate at 13.56 MHz or any other acceptable frequency.Also, the attachment may provide for a passive communication mode, wherethe initiator device provides a carrier field, permitting answers by thetarget device via modulation of existing fields. Additionally, theattachment may also provide for an active communication mode by allowingalternate field generation by the initiator and target devices.

To utilize dynamic transaction cards to facilitate the mobile moneytransfer, the active NFC communication mode must be enabled for thedynamic transaction cards. The system may evaluate whether the activeNFC communication mode is enabled for the first customer dynamictransaction card at block 504, and for the second customer dynamictransaction card at block 510. As such if the active NFC communicationmode for the first dynamic transaction card is not enabled, the processmay end at block 506. If the active communication mode for the seconddynamic transaction card is not enabled, the process may end at block512.

Based on the operating system of a mobile device, a mobile applicationon the device may have both an active NFC mode and a passive/reader NFCmode, or may be limited to only having a passive/reader NFC mode. Assuch a mobile device having only a passive reader mode may not beutilized to facilitate a mobile funds transfer. However, the systemconfiguration described herein utilizing dynamic transaction cards inconjunction with a mobile application transforms the mobile applicationto an interoperable application that may be utilized across differentoperating systems, providing an operating system neutral mobile fundstransfer system.

At block 508, the first customer dynamic transaction card of thecustomer requesting to make the transfer of funds may be placed incontact with the second recipient customer dynamic transaction card ofthe recipient customer receiving the funds transfer to establish an NFCconnection. The first customer dynamic transaction card may receive aresponse from the second recipient customer dynamic transaction cardconfirming an NFC connection between the two cards.

At block 514 the application processor on the second recipient customerdynamic transaction card may be utilized to generate a passive NFC tag,which may be utilized to securely store second customer accountinformation in the passive NFC tag. As such, sensitive customer accountinformation does not need to be entered to facilitate the funds transferand may be obtained through the NFC connection. Utilizing this NFCconnection, the first customer dynamic transaction card requesting thetransfer of funds may obtain, via the NFC antenna on the card, therecipient customer account information stored on the passive NFC tag atblock 516. A user may be issued a unique identified stored on thedynamic transaction card's NFC tag rather than storing personalinformation such as a customer name, zip code, email address, etc.

At block 518, to facilitate the mobile transfer of funds, the firstdynamic transaction card requesting the transfer of funds may transmit,via a Bluetooth™ or BLE network, the recipient account information to amobile application which may be located on a mobile device of thecustomer requesting the funds transfer. The mobile application maytransmit the recipient account information to an account provider systemvia a mobile network or WiFi, where the information may be passed andqueued on the backend account provider system to complete the transfer.The transaction system of the account provider system may be utilized totransfer the requested funds from the first requesting customer accountto the second recipient customer account at block 520. A destination APImay be utilized in order to provide a confirmation regarding thetransfer of funds to, for example, a source financial institution. Theprocess may end at block 522. The transaction system may transmit amessage to the account provider system notifying the account provider ofthe funds transfer. The notification may be utilized by the accountprovider system to update the associated account balances to reflect thetransfer of funds.

The request for a mobile funds transfer may be processed using thesystems described in FIGS. 1, 2, 3, 4, Data may be securely transmittedbetween a mobile device 302 and a financial institution. Moreover, amobile banking application and/or a financial institution applicationmay provide a secure connection and/or security features (e.g.,cryptographic keys, protocol, hash algorithm, digital signatures,passwords, checksums, and/or the like) to conduct secure communicationswith a financial institution backend and receive updated financial datato transmit, via RFID, BLE, Bluetooth™, NFC, and/or the like, to adynamic transaction card for storage and/or display.

For example, a mobile application may communicate with a backend accountprovider system via a mobile network or WiFi to pass customer/accountinformation to the backend to facilitate the transfer of funds. Customeraccount information may be encrypted to facilitate a secure transfer ofthe information. The transmitted information may include a key or tokenof encrypted information representing a financial account, the amount ofthe transaction and/or other information necessary to facilitate thetransfer of funds. The backend account provider system may verify thecustomer account information, as it may use the customer accountinformation to look up the account of the customer and determine whetherthe transfer of funds should be authorized. The account provider systemmay check the account information against certain parameters todetermine, for example, whether the transfer complies with certainparameters, and/or whether the associated token has expired.

An API may also encrypt, for example account and routing numbers toensure that any passing customer account identifying data is secureduring transmission and storage. The data may be read and encryptedusing a private key stored within the dynamic transaction cardprocessor. First device also may store instructions to encrypt and/orencode data being transmitted from the first device. A first device maystore instructions to decrypt and/or decode data received at the firstdevice. A first device may store encryption/encoding/decryption/decodinginstruction in a secure element or a secure microprocessor. For example,where a first device includes an EMV™ chip,encryptions/encoding/decryption/decoding instructions may be storedwithin the EMV™ chip. A first device may store instructions to validatea public/private key handshake between the first device and a seconddevice to pair the first device and second device via a Bluetooth™/BLEconnection.

It is further noted that the systems and methods described herein may betangibly embodied in one of more physical media, such as, but notlimited to, a compact disc (CD), a digital versatile disc (DVD), afloppy disk, a hard drive, read only memory (ROM), random access memory(RAM), as well as other physical media capable of storing software, orcombinations thereof. Moreover, the figures illustrate variouscomponents (e.g., servers, computers, processors, etc.) separately. Thefunctions described as being performed at various components may beperformed at other components, and the various components bay becombined or separated. Other modifications also may be made.

The present disclosure is not to be limited in terms of the particularembodiments described in this application, which are intended asillustrations of various aspects. Many modifications and variations canbe made without departing from its spirit and scope, as may be apparent.Functionally equivalent methods and apparatuses within the scope of thedisclosure, in addition to those enumerated herein, may be apparent fromthe foregoing representative descriptions. Such modifications andvariations are intended to fall within the scope of the appendedrepresentative claims. The present disclosure is to be limited only bythe terms of the appended representative claims, along with the fullscope of equivalents to which such representative claims are entitled.It is also to be understood that the terminology used herein is for thepurpose of describing particular embodiments only, and is not intendedto be limiting.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It may be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It may be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent may be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should be interpreted to mean “at least one”or “one or more”); the same holds true for the use of definite articlesused to introduce claim recitations. In addition, even if a specificnumber of an introduced claim recitation is explicitly recited, suchrecitation should be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, means at least two recitations, or two or more recitations).Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It may be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” may be understood toinclude the possibilities of “A” or “B” or “A and B.”

The foregoing description, along with its associated embodiments, hasbeen presented for purposes of illustration only. It is not exhaustiveand does not limit the invention to the precise form disclosed. Thoseskilled in the art may appreciate from the foregoing description thatmodifications and variations are possible in light of the aboveteachings or may be acquired from practicing the disclosed embodiments.For example, the steps described need not be performed in the samesequence discussed or with the same degree of separation. Likewisevarious steps may be omitted, repeated, or combined, as necessary, toachieve the same or similar objectives. Accordingly, the invention isnot limited to the above-described embodiments, but instead is definedby the appended claims in light of their full scope of equivalents.

In the preceding specification, various preferred embodiments have beendescribed with references to the accompanying drawings. It may, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded asan illustrative rather than restrictive sense.

1. A dynamic transaction card comprising: a secure payment chip thatstores financial data; a payment processing microprocessor; and anapplication processor storing a first application, wherein the firstapplication when executed causes the dynamic transaction card to:receive, via a short range wireless communication network, a request,from a user application executed on a user device, to transfer fundsfrom a first account associated with the dynamic transaction card to asecond account associated with a second recipient dynamic transactioncard; enable an active communication mode on the dynamic transactioncard; contact the second recipient dynamic transaction card, wherein thesecond recipient dynamic transaction card enables an activecommunication mode and stores second recipient account information in apassive tag; receive, via a connection between the dynamic transactioncard and the second recipient dynamic transaction card, the secondrecipient account information stored in the passive tag; and transmit,via the short range wireless communication network, the second recipientaccount information to the user application, wherein: the userapplication transmits the second account information to an accountprovider system over a mobile network or WiFi; and the account providersystem transfers the requested funds from the first account to thesecond recipient account.
 2. The dynamic transaction card of claim 1,wherein the secure payment chip comprises a EuroPay-MasterCard-Visa(EMV™) chip.
 3. The dynamic transaction card of claim 1, wherein theuser device comprises a mobile device.
 4. The dynamic transaction cardof claim 1, wherein the connection between the dynamic transaction cardand the second recipient dynamic transaction card comprises a Near FieldCommunication (NFC) connection.
 5. The dynamic transaction card of claim1, wherein the short range wireless communication network comprises aBluetooth™ or Bluetooth™ Low Energy (BLE) network.
 6. A methodcomprising: receiving on a first dynamic transaction card applicationprocessor, via a short range wireless communication network, a request,from a user application executed on a user device, to transfer fundsfrom a first account associated with a first dynamic transaction card toa second recipient account associated with a second recipient dynamictransaction card; enabling, via the first dynamic transaction cardapplication processor, an active communication mode on the first dynamictransaction card; enabling, via a second dynamic transaction cardapplication processor, a second active communication mode on the seconddynamic transaction card; and storing, via the second dynamictransaction card application processor, a second account information ina passive NFC tag; establishing an NFC connection by contacting thefirst dynamic transaction card to the second dynamic transaction card;receiving, via a connection between the first dynamic transaction cardand the second recipient dynamic transaction card, the second accountinformation stored in the passive tag; transmitting, via the short rangewireless communication network, the second account information from thefirst dynamic transaction card to the user application; transmitting,via the user application, the second account information to an accountprovider system over a wireless network; and transferring the requestedfunds, via the account provider system, from the first account to thesecond recipient account.
 7. The method of claim 6, wherein the userdevice comprises a mobile device.
 8. The method of claim 6, wherein theconnection between the dynamic transaction card and the second recipientdynamic transaction card comprises a Near Field Communication (NFC)connection.
 9. The method of claim 6, wherein the short range wirelesscommunication network comprises a Bluetooth™ or Bluetooth™ Low Energy(BLE) network.
 10. The method of claim 6, wherein the wireless networkcomprises a mobile network or WiFi.